Autogenerated HTML docs for v1.5.6.1-156-ge903b 
diff --git a/git-branch.txt b/git-branch.txt index 0fd5808..5e78aed 100644 --- a/git-branch.txt +++ b/git-branch.txt 
@@ -8,12 +8,12 @@  SYNOPSIS  --------  [verse] -'git-branch' [--color | --no-color] [-r | -a] [--merged | --no-merged] +'git branch' [--color | --no-color] [-r | -a] [--merged | --no-merged]  [-v [--abbrev=<length> | --no-abbrev]]  [--contains <commit>] -'git-branch' [--track | --no-track] [-l] [-f] <branchname> [<start-point>] -'git-branch' (-m | -M) [<oldbranch>] <newbranch> -'git-branch' (-d | -D) [-r] <branchname>... +'git branch' [--track | --no-track] [-l] [-f] <branchname> [<start-point>] +'git branch' (-m | -M) [<oldbranch>] <newbranch> +'git branch' (-d | -D) [-r] <branchname>...    DESCRIPTION  ----------- @@ -37,7 +37,7 @@  new branch.    When a local branch is started off a remote branch, git sets up the -branch so that linkgit:git-pull[1] will appropriately merge from +branch so that `git-pull` will appropriately merge from  the remote branch. This behavior may be changed via the global  `branch.autosetupmerge` configuration flag. That setting can be  overridden by using the `--track` and `--no-track` options. @@ -54,7 +54,7 @@    Use -r together with -d to delete remote-tracking branches. Note, that it  only makes sense to delete remote-tracking branches if they no longer exist -in remote repository or if linkgit:git-fetch[1] was configured not to fetch +in remote repository or if `git-fetch` was configured not to fetch  them again. See also 'prune' subcommand of linkgit:git-remote[1] for way to  clean up all obsolete remote-tracking branches.   @@ -107,14 +107,14 @@ 	Display the full sha1s in output listing rather than abbreviating them.    --track:: -	When creating a new branch, set up configuration so that git-pull +	When creating a new branch, set up configuration so that `git-pull` 	will automatically retrieve data from the start point, which must be 	a branch. Use this if you always pull from the same upstream branch 	into the new branch, and if you don't want to use "git pull 	<repository> <refspec>" explicitly. This behavior is the default 	when the start point is a remote branch. Set the 	branch.autosetupmerge configuration variable to `false` if you want -	git-checkout and git-branch to always behave as if '--no-track' were +	`git-checkout` and `git-branch` to always behave as if '--no-track' were 	given. Set it to `always` if you want this behavior when the 	start-point is either a local or remote branch.